The characteristics described below are common between the uniexp, uniimp and package commands.
These commands connect to UVMS to retrieve authentication information; then they connect directly to the target node to extract information (like UVC could do it).
If several filters address the same object type, all the filters are combined to extract/import the object (AND logic).
For example a uniexp command which contains the parameters -jeses="SES*" -jemu="*MU*" extracts all the job events with a session that starts with “SES” and a MU which contains “MU”.
If the same filter is used several times with different values, only the first value is taken into account
For example: -upr "A*" -upr "B*", only the Uprocs starting with A are extracted/imported.
The * character can be used at the start or end of the chain.
For example: "TEST*" signifies “starting with TEST”, "*TEST" signifies “ends with TEST”, "*TEST*" signifies “contains TEST”.
Environment variables
Two environment variables allow you to adjust the memory used by the import-export commands.
The user can change this value before launching import, export or update commands by using system commands:
On Unix:
UXMINJVMMEM=256
export UXMINJVMMEM
UXMAXJVMMEM=2048
export UXMAXJVMMEM
On Windows:
set UXMINJVMMEM=256
set UXMAXJVMMEM=2048
Return Codes
The command returns:
In case the result of the command is long, it is recommended to redirect stdout and stderr to a file. For example:
./uniexp [param=valeur] > ./export.log 2>&1"
As of version 6.10.41, documentation new updates are posted on the Broadcom Techdocs Portal.
Look for Dollar Universe.